This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
EVEREST-633 Install monitoring stack onto a separate namespace #281
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
recharte
force-pushed
the
EVEREST-633-multi-namespaces-monitoring
branch
from
8a9ac71 to
df75192
Compare
By moving to a multi-namespace everest-operator installation we configured the operator group of the percona-everest namespace to have N target namespaces. The VM Operator doesn't support multi-namespaces so we can't deploy it to the same namespace as the everest-operator. Therefore we install it onto a separate namespace for managing everything monitoring related.
recharte
force-pushed
the
EVEREST-633-multi-namespaces-monitoring
branch
from
020692d to
dd24375
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## EVEREST-495-multi-namespaces #281 +/- ##
==============================================================
Coverage ? 5.31%
==============================================================
Files ? 12
Lines ? 2693
Branches ? 0
==============================================================
Hits ? 143
Misses ? 2525
Partials ? 25 ☔ View full report in Codecov by Sentry. |
ghost
approved these changes
Feb 6, 2024
oksana-grishchenko
approved these changes
Feb 6, 2024
recharte
force-pushed
the
EVEREST-633-multi-namespaces-monitoring
branch
from
1972bc6 to
1675d32
Compare
recharte
added a commit
that referenced
this pull request
Feb 7, 2024
* EVEREST-633 install monitoring stack with install command By moving to a multi-namespace everest-operator installation we configured the operator group of the percona-everest namespace to have N target namespaces. The VM Operator doesn't support multi-namespaces so we can't deploy it to the same namespace as the everest-operator. Therefore we install it onto a separate namespace for managing everything monitoring related. * EVEREST-633 remove monitoring command * EVEREST-633 Update everest-operator go mod * EVEREST-633 Update percona-everest-backend go mod * EVEREST-633 forbid installs in the monitoring namespace * EVEREST-633 update namespaces env var name * EVEREST-633 Update everest-operator go mod
3 tasks
recharte
added a commit
that referenced
this pull request
Feb 7, 2024
* EVEREST-633 Add multi-namespace support (#271) * EVEREST-633 force everest install to percona-everest namespace * EVEREST-633 remove deprecated name flag * EVEREST-633 add multi-namespace support * EVEREST-633 remove operator channel flags * EVEREST-633 update backend and operator go mods * EVEREST-633 shut up linter, we know this code is dead * EVEREST-633 Install monitoring stack onto a separate namespace (#281) * EVEREST-633 install monitoring stack with install command By moving to a multi-namespace everest-operator installation we configured the operator group of the percona-everest namespace to have N target namespaces. The VM Operator doesn't support multi-namespaces so we can't deploy it to the same namespace as the everest-operator. Therefore we install it onto a separate namespace for managing everything monitoring related. * EVEREST-633 remove monitoring command * EVEREST-633 Update everest-operator go mod * EVEREST-633 Update percona-everest-backend go mod * EVEREST-633 forbid installs in the monitoring namespace * EVEREST-633 update namespaces env var name * EVEREST-633 Update everest-operator go mod * EVEREST-633 Use PGO stable channel (#282) * EVEREST-633 install monitoring stack with install command By moving to a multi-namespace everest-operator installation we configured the operator group of the percona-everest namespace to have N target namespaces. The VM Operator doesn't support multi-namespaces so we can't deploy it to the same namespace as the everest-operator. Therefore we install it onto a separate namespace for managing everything monitoring related. * EVEREST-633 remove monitoring command * EVEREST-633 Update everest-operator go mod * EVEREST-633 Update percona-everest-backend go mod * EVEREST-633 forbid installs in the monitoring namespace * EVEREST-633 use PGO stable channel * EVEREST-495 Update everest-operator go mod * EVEREST-495 Fix missing monitoring namespace env var
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Install monitoring stack onto a separate namespace
Problem:
EVEREST-633
By moving to a multi-namespace everest-operator installation we configured the operator group of the percona-everest namespace to have N target namespaces.
The VM Operator doesn't support multi-namespaces so we can't deploy it to the same namespace as the everest-operator.
Therefore we install the monitoring stack onto a separate namespace for managing everything monitoring related.
CHECKLIST
Jira
Tests
[ ] Is an Integration test/test case added for the new feature/change?[ ] Are unit tests added where appropriate?